| Message | The calculation of where to grab data from the fuel/timing maps also utilizes the current TP value, I dunno if you calculate that or not externally. A super sporty option would ultimately keep the consult protocol and add onto it, so you could interface everything into a single hardware piece (cost factor as you mentioned, footprint, etc), and based on the extended protocol you'd know if you were currently receiving a consult data byte, or some type of external sensor/hardware data byte and then process accordingly. Good luck with the project, any plans for windows mobile at all or are you sticking to Palm? Mike
 
 |  |